Configurations Using Microservices
To make certain modifications in the Temenos DigitalOrigination app, you must update the information in the relevant microservices.
Marketing Catalog Microservice (MCMS)
The Product Dashboard and the Product Selection modules in the Temenos DigitalOrigination app display information about the available products and their features. This information is retrieved from the Marketing Catalog Microservice (MCMS). If the data in the MCMS changes, the information displayed on the app also changes dynamically at the run time.
To ensure data integrity, the data in MCMS and the Core (Temenos Transact for example) is always in sync. The information in MCMS, such as the product names and features, is retrieved from the Core since these attributes are mapped to the core system. To know more about the data synchronization between MCMS and the Core for the attributes that are mapped to the core, click here.
However, some extended attributes, such as Product Descriptions, are introduced for the front end and are not mapped to the Core system. These attributes can be managed at the MCMS layer only. From 2020.10 release, the product related information in the Temenos DigitalOrigination app can be configured from Spotlight > Master Data Management > Products. For more information on configuring the Product details from Spotlight, click here.
Data synchronization between MCMS and Core
Initially, the data in the MCMS is ingested from the Core (Temenos Transact or other core systems). The standard product details that are retrieved from the Core during the process of ingestion are listed in the following field mapping table.
MS Attribute | Description |
---|---|
productLineRef | The top-level product line in which the product is ultimately attached |
productLineName | Specifies the display name of the Product Line |
externalIndicator | Indicates the external product line |
productGroupRef | The groups under a specific product line in which the product is ultimately grouped. |
branchRef | Unique identifier of the branch |
productLineRef | The top-level product line in which the product is ultimately attached |
externalIndicator | Indicates the external product group |
productRef | Unique identifier for the product in the core banking system |
productName | Specifies the display name of the Product |
productLine | The top-level product line in which the product is ultimately attached |
productGroup | The groups under a specific product line in which the product is ultimately grouped. |
branchRef | Unique identifier of the branch |
availableFrom | Date from when the product is available. |
availableTo | Date until when the product is available. |
ProductFeatures
|
|
Option Value
|
Specifies the available customer option for the product features |
currency | Currency of the product |
For more details on the mapping of these attributes from Temenos Transact to MCMS, click here.
Whenever a product’s details are updated in Temenos Transact, an ingestion is triggered.
Consider that you configured the value of any of these attributes (that are mapped to the core system) in MCMS. During the next ingestion, the values of all the core attributes in the MCMS are overridden by the values that are present in the core system. Therefore, the attribute value that you modified before the ingestion is overridden with the value in the core system again. Therefore, it is always suggested that these attributes must not be modified.
You can however modify other attributes that are not mapped for ingestion. For example, the attributes that are created directly on the MCMS are not mapped to the core. Therefore, the values of these attributes remain unchanged even after ingestion. For more information on how to modify the configurable product details, click here.
In this topic